If the METOPT utility encounters critical errors, such as the inability to find or open a file, while it is running, it will notify you and stop immediately. Common critical errors include:
The METOPT utility can also report actual or potential non-critical problems it encounters while it runs. For instance, if the utility finds Metacode records that may prevent the file from printing, it can warn you. These non-critical errors usually fall into two categories:
To have this utility notify you if it spots potential problems, add the following option to your PrtType:XER control group:
< PrtType:XER >
ValidLevel =
Option |
Description |
0 |
Enter zero (0) to tell the utility not to report non-critical problems. This is the default. |
1 |
Enter one (1) to tell the utility to report warnings for non-critical problems, but continue optimizing. |
2 |
Enter two (2) to tell the utility to report warnings for non-critical problems and attempt to fix the problems |
3 |
Enter three (3) to tell the utility to report warnings for non-critical problems and exit immediately |
Using the ValidLevel option gives you a degree of control over how certain errors are handled. Keep in mind that, although classified as non-critical, many of these errors can produce invalid output. So, many of the more severe non-critical errors will be promoted automatically by METOPT to a ValidLevel of 3. METOPT will then display the error and stop executing. Such instances usually fall into the first category described above.
Usually, the non-critical errors that do not force METOPT to stop processing involve one corrupt record, such as a record that contains an invalid Metacode sequence. In most cases, if you set the ValidLevel option to 1, a warning appears and the record displays, but the utility continues to process the record.
For the same record, if you set ValidLevel to 2, the same warnings appear, but this time the record is not processed with the others. So, since that record is left alone, the printer will treat it as it would have the identical record in the input file.
You can also use the following INI option to help track down and resolve errors:
< PrtType:XER >
SaveComment =
The SaveComment option lets you save the last Metacode comment record processed and display it when an error is encountered. This can be a helpful placeholder when you are trying to isolate the location of an error record in a large file. If the Metacode file contains occasional or frequent comment records, then the SaveComment option can be a useful troubleshooting tool.
The possible values for the SaveComment option are:
Option |
Description |
(blank) |
Do not save comments. This is the default. |
S |
Display the last comment as-is, with no conversion. |
A |
Convert the last comment to ASCII, then display. |
E |
Convert the last comment to EBCDIC, then display. |
H |
Display the last comment in hexadecimal. |
© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.